Fix update command incorrectly reports "already at latest" after successful update#35
Merged
Conversation
The update command now checks for available updates BEFORE running the update process, stores the expected new version, and reports that version after successful update. This fixes the issue where running "cratis update" would always show "Already at the latest version" even when an update was available, because the currently running process version cannot change until the CLI is restarted. Also added user guidance that the new version will be active when they run 'cratis' again.
Copilot
AI
changed the title
[WIP] Fix update command to detect new versions correctly
Fix update command incorrectly reports "already at latest" after successful update
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
cratis updatecommand updates the on-disk binary but then checks the version of the currently running process, which hasn't changed. This caused it to report "Already at the latest version (1.6.1)" even after successfully installing 1.6.2.Fixed